Support for tag-driven publishing on Travis.#39
Merged
adriaanm merged 2 commits intoscala:masterfrom Dec 4, 2014
Merged
Conversation
Modify travis build to derive the project version from TRAVIS_TAG (when set).
as well as to have sbt run the `publish-signed` task if the environment is right.
The tag must match the semver regex `^v[0-9]+\.[0-9]+\.[0-9]+(-[A-Za-z0-9-]+)?`,
and the jdk we're running on must match PUBLISH_JDK (set in .travis.yml).
For every repo, you must create the following files (not included here)
according to the instructions in admin/gpg.sbt:
- admin/pubring.asc (commit)
- admin/secring.asc (DO NOT COMMIT)
- sensitive.sbt (DO NOT COMMIT)
- passphrase for secring.asc
- api token for staging to sonatype
Generate these using `admin/encryptAll.sh`:
- admin/secring.asc.enc (commit)
- sensitive.sbt.enc (commit)
Note that `encryptAll.sh` spits out a "- secure .... " line,
that you need to add to `.travis.yml`'s `env` section, so that
travis can supply the SECRET env variable, which is used to
decrypt the sensitive files above.
Contributor
Author
|
This will need to be tested by creating an RC tag. |
adriaanm
added a commit
that referenced
this pull request
Dec 4, 2014
Support for tag-driven publishing on Travis.
Contributor
Author
|
@gourlaysama, you can now stage a release on sonatype simply by creating a tag in the GitHub interface! Someone on the core team still needs to close and promote the staging repo on sonatype. To ping us for that, I suggest creating an issue here and assigning to one of us once the Travis build is done. |
Contributor
Author
|
PS: I had to upgrade to sbt 0.13.7 for the script to work. I hope that's ok. |
Contributor
|
This is great! I'm slightly late to the party, but I'll push a tag ASAP. |
Contributor
Author
|
Ok! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Modify travis build to derive the project version from TRAVIS_TAG (when
set). as well as to have sbt run the
publish-signedtask if theenvironment is right. The tag must match the semver regex
^v[0-9]+\.[0-9]+\.[0-9]+(-[A-Za-z0-9-]+)?, and the jdk we're running onmust match PUBLISH_JDK (set in .travis.yml).
For every repo, you must create the following files (not included here)
according to the instructions in admin/gpg.sbt:
Generate these using
admin/encryptAll.sh:Note that
encryptAll.shspits out a "- secure .... " line, that you needto add to
.travis.yml'senvsection, so that travis can supply theSECRET env variable, which is used to decrypt the sensitive files above.